Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark previously deprecated SSL settings as obsolete #1197

Merged

Conversation

donoghuc
Copy link
Contributor

  • SSL settings that were marked deprecated in version 11.14.0 are now marked obsolete, and will prevent the plugin from starting.
  • These settings are:
    • cacert, which should be replaced by ssl_certificate_authorities
    • keystore, which should be replaced by ssl_keystore_path
    • keystore_password, which should be replaced by ssl_keystore_password
    • ssl, which should be replaced by ssl_enabled
    • ssl_certificate_verification, which should be replaced by ssl_verification_mode
    • truststore, which should be replaced by ssl_truststore_path
    • truststore_password, which should be replaced by ssl_truststore_password

Thanks for contributing to Logstash! If you haven't already signed our CLA, here's a handy link: https://www.elastic.co/contributor-agreement/

Closes #1190

@donoghuc donoghuc force-pushed the GH-1190-mark-ssl-opts-obsolete branch from 2c81627 to 6cc1624 Compare December 10, 2024 21:36
Copy link
Contributor

@robbavey robbavey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code LGTM, over to @karenzone for docs approval

@donoghuc
Copy link
Contributor Author

Corresponding LS deprecation docs PR elastic/logstash#16787

@donoghuc
Copy link
Contributor Author

I came up with a workflow to run the acceptance tests in LS against these changes un this branch https://github.com/elastic/logstash/tree/test-plugin-from-gh-source-buildkite-run CI runs https://buildkite.com/elastic/logstash-pull-request-pipeline/builds/1958 are red but it appears to be due to installing a gem from GH source instead of ssl deprecation issues. So i think this should not cause any issues once it promotes into LS.

Copy link
Contributor

@karenzone karenzone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

DO NOT MERGE: We'll need to review and merge this fix (elastic/logstash#16798) first to avoid breaking the docs build. Then, I'll re-test to be sure we're good to go.

Comment on lines 1419 to 1422
[id="plugins-{type}s-{plugin}-common-options"]
include::{include_path}/{type}.asciidoc[]

:no_codec!:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs to be at the end of every plugin doc file.
Please add it back. :-)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OH, wow, yeah my bad! Thanks for catching that.

Copy link
Contributor

@karenzone karenzone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Line 328-329: Please change to

"This plugin supports these configuration options plus the <<plugins-{type}s {plugin}-common-options>> described later."

To resolve:

  • bad link causing docs build to fail
  • inaccurate information (that we're continue to support deleted settings)

Copy link
Contributor

@karenzone karenzone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Line 443:
Please change <<plugins-{type}s-{plugin}-ssl,ssl_enabled => true>> to
<<plugins-{type}s-{plugin}-ssl_enabled,ssl_enabled => true>>.

It's looking for the now deleted ssl setting.

(GitHub won't allow me to comment on lines not included in this PR. )

@karenzone
Copy link
Contributor

@donoghuc, after pulling down your latest update and making that last fix noted Line 443, I'm getting a passing doc build. We're so close!

Ugh... now we have some rendering problems. I'll have those for you shortly.

docs/index.asciidoc Outdated Show resolved Hide resolved
docs/index.asciidoc Outdated Show resolved Hide resolved
Copy link
Contributor

@karenzone karenzone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change didn't get implemented and is causing the doc build to fail.

#1197 (review)

@donoghuc
Copy link
Contributor Author

This change didn't get implemented and is causing the doc build to fail.

#1197 (review)

Sorry, that got lost in the shuffle. Updated in 7c4be65

@karenzone
Copy link
Contributor

GitHub won't let me make suggestions to lines that didn't have changes. That's the reason, I have to note these as general suggestions with Line numbers.

WARNING: As of version `12.0.0` of this plugin, some configuration options have been replaced.
The plugin will fail to start if it contains any of these obsolete options.

[cols="<,<",options="header",]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Delete extra space before delimiters in table (lines 1333 and 1342)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated in 8282103

@@ -1330,7 +1330,7 @@ WARNING: As of version `12.0.0` of this plugin, some configuration options have
The plugin will fail to start if it contains any of these obsolete options.

[cols="<,<",options="header",]
|=======================================================================
=======================================================================
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The pipe in Line 1333 needs to stay, please.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤦 i'm really doing poorly today. Need more coffee.

- `truststore`, which should be replaced by `ssl_truststore_path`
- `truststore_password`, which should be replaced by `ssl_truststore_password`
- [#1197](https://github.com/logstash-plugins/logstash-output-elasticsearch/pull/1197)

## 11.22.10
- Add `x-elastic-product-origin` header to Elasticsearch requests [#1194](https://github.com/logstash-plugins/logstash-output-elasticsearch/pull/1194)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NO CHANGE NEEDED HERE.

ON MERGE, we might have a conflict to resolve. Please be sure to keep what's currently in source.
The correct PR number is #1195.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can explicitly rebase against main and push that to this branch. Locally that looks right, i'll push so there is no confusion.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pushed the rebase, it looks correct in the expanded diff now :)

donoghuc and others added 8 commits December 23, 2024 15:47
 - SSL settings that were marked deprecated in version `11.14.0` are now marked
   obsolete, and will prevent the plugin from starting.
  - These settings are:
    - `cacert`, which should be replaced by `ssl_certificate_authorities`
    - `keystore`, which should be replaced by `ssl_keystore_path`
    - `keystore_password`, which should be replaced by `ssl_keystore_password`
    - `ssl`, which should be replaced by `ssl_enabled`
    - `ssl_certificate_verification`, which should be replaced by
      `ssl_verification_mode`
    - `truststore`, which should be replaced by `ssl_truststore_path`
    - `truststore_password`, which should be replaced by
      `ssl_truststore_password`
Restore the deleted EOF as it is required for docs.
Replace ssl with ssl_enabled.
@donoghuc donoghuc force-pushed the GH-1190-mark-ssl-opts-obsolete branch from bd5833f to 41058cb Compare December 23, 2024 22:49
Copy link
Contributor

@karenzone karenzone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Builds cleanly, renders as expected, and LGTM! 🚀

@donoghuc
Copy link
Contributor Author

Amazing! thanks so much for all the help (and patience) on this one.

@donoghuc donoghuc merged commit de61518 into logstash-plugins:main Dec 24, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove deprecated SSL settings from Elasticsearch output
3 participants